Hi👋, please ensure the PR title follows the below standards:

• PR is titled with conventional commit style naming: type(scope): message. For example: feat(passport): my new feature
• If you have introduced modification that necessitates immediate adjustments by this SDK's users to their applications, clients, or integrations to avert disruptions to existing features or functionalities, add a ! after the type(scope), for example feat(passport)!: my new breaking feature

Summary

Fall through to throwing an error when the guardian responds with a 422 for transaction evaluation for non-native clients.

Detail and impact of the change

The sdk checks the response code when simulating transactions.

      if (isAxiosError(error) && error.response?.status === 422) {
        if (this.crossSdkBridgeEnabled) {
          const revertReason = (error.response?.data as any)?.message ?? 'A transaction simulation reverted';
          throw new JsonRpcError(
            RpcErrorCode.TRANSACTION_REVERTED,
            `Transaction will revert: ${revertReason}`,
          );
        }

        return { confirmationRequired: true };
      }

When the response code is a 422 and crossSdkBridgeEnabled is true (native clients), the sdk will throw an error. However, there is a bug in this flow, where if crossSdkBridgeEnabled is false, the sdk would instead return an invalid { confirmationRequired: true } response.

This particular path is dead-code, as the guardian service only returns 422 for native clients. However, it is still preferable to remove it and improve the clarity of the flow.

Added

Changed

Deprecated

Removed

Fixed

Security

Anything else worth calling out?